Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a067daf4d8f262e773efaa1f93c9f5437f1909d854a20c00729fa2b982046a0

Tx prefix hash: 0ff2dadaac2c1656f541669664e5ee16eb3badef9812b9536b8895ea93f5bde8
Tx public key: 3160fcfbbe3332f38270c358aeafa18ac77d1e329b29f63dc6c0b7c15db15008
Timestamp: 1708326396 Timestamp [UCT]: 2024-02-19 07:06:36 Age [y:d:h:m:s]: 01:286:14:51:11
Block: 960775 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 463628 RingCT/type: yes/0
Extra: 013160fcfbbe3332f38270c358aeafa18ac77d1e329b29f63dc6c0b7c15db150080211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6136d2f7abf8cc47f65ce560c0d38b72b284ce3a8b04dbd2a3e9ae2c2a04404 0.600000000000 1420362 of 15

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": 960785, "vin": [ { "gen": { "height": 960775 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6136d2f7abf8cc47f65ce560c0d38b72b284ce3a8b04dbd2a3e9ae2c2a04404" } } ], "extra": [ 1, 49, 96, 252, 251, 190, 51, 50, 243, 130, 112, 195, 88, 174, 175, 161, 138, 199, 125, 30, 50, 155, 41, 246, 61, 198, 192, 183, 193, 93, 177, 80, 8, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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