Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8633b0e749b6b9f3f7221d8d0c871aa6bb0333b0b5118a7a9ca37a02c268806d

Tx prefix hash: a9370c461ccc7b46cd5fb2287ff96c6eacf2cc9f345308d52458a80ed63a9ff9
Tx public key: 135ede1dc74afa31cc95fea5b0a4caa01889568e626370d1d6390e342746e8f1
Timestamp: 1574091409 Timestamp [UCT]: 2019-11-18 15:36:49 Age [y:d:h:m:s]: 05:107:16:35:02
Block: 11623 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1220201 RingCT/type: yes/0
Extra: 01135ede1dc74afa31cc95fea5b0a4caa01889568e626370d1d6390e342746e8f102110000000166a80d00000000000000000000

1 output(s) for total of 561.680135979000 dcy

stealth address amount amount idx
00: ca2a70a6425c19df874b169ffb10625c05ff151e394d22baee069b29f5911188 561.680135979000 12700 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": 11633, "vin": [ { "gen": { "height": 11623 } } ], "vout": [ { "amount": 561680135979, "target": { "key": "ca2a70a6425c19df874b169ffb10625c05ff151e394d22baee069b29f5911188" } } ], "extra": [ 1, 19, 94, 222, 29, 199, 74, 250, 49, 204, 149, 254, 165, 176, 164, 202, 160, 24, 137, 86, 142, 98, 99, 112, 209, 214, 57, 14, 52, 39, 70, 232, 241, 2, 17, 0, 0, 0, 1, 102, 168, 13, 0, 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