Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 4005bd3ec8d0373514d6cd8ceca2bbbcc073cd3f34ee0c3f8d2fcae53eee442c

Tx prefix hash: cb92b7e35ffb99e8f91a0bc3a3266de08ff39f4c081416ae8a8142877cc839b6
Tx public key: 3d17f6aaaa23d75c16fdecf0b80372f5212b618ab06a5ab0cae93de404ce066a
Timestamp: 1672755733 Timestamp [UCT]: 2023-01-03 14:22:13 Age [y:d:h:m:s]: 02:170:12:01:29
Block: 666742 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 643412 RingCT/type: yes/0
Extra: 013d17f6aaaa23d75c16fdecf0b80372f5212b618ab06a5ab0cae93de404ce066a02110000000452542ceb000000000000000000

1 output(s) for total of 3.791464013000 dcy

stealth address amount amount idx
00: 3327a7391e186ff1637eebc8e989deeebd45d608946c41b209cfaaf874fe5a0c 3.791464013000 1107879 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 666752, "vin": [ { "gen": { "height": 666742 } } ], "vout": [ { "amount": 3791464013, "target": { "key": "3327a7391e186ff1637eebc8e989deeebd45d608946c41b209cfaaf874fe5a0c" } } ], "extra": [ 1, 61, 23, 246, 170, 170, 35, 215, 92, 22, 253, 236, 240, 184, 3, 114, 245, 33, 43, 97, 138, 176, 106, 90, 176, 202, 233, 61, 228, 4, 206, 6, 106, 2, 17, 0, 0, 0, 4, 82, 84, 44, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8