Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ebf64be52b799e51b539c88b96a071f69f0d5515c0850d8017981ea64464e695

Tx prefix hash: c1e3a5cee85dfd6f6040e444ec17fa569f1be69388cb2b6cf95950b1f4cc701b
Tx public key: 764d2f87d197e573248e7ca6dbab79e199da0aa3f22dadc011e656789c8a6a12
Timestamp: 1629378821 Timestamp [UCT]: 2021-08-19 13:13:41 Age [y:d:h:m:s]: 03:199:14:47:56
Block: 317120 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 916016 RingCT/type: yes/0
Extra: 01764d2f87d197e573248e7ca6dbab79e199da0aa3f22dadc011e656789c8a6a1202110000001301f1e57f000000000000000000

1 output(s) for total of 54.607244524000 dcy

stealth address amount amount idx
00: 1d74fe3ba20a911110ee13e806ea03b937ddc01b5e9de5909f5aeddeb1f16a26 54.607244524000 659497 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": 317130, "vin": [ { "gen": { "height": 317120 } } ], "vout": [ { "amount": 54607244524, "target": { "key": "1d74fe3ba20a911110ee13e806ea03b937ddc01b5e9de5909f5aeddeb1f16a26" } } ], "extra": [ 1, 118, 77, 47, 135, 209, 151, 229, 115, 36, 142, 124, 166, 219, 171, 121, 225, 153, 218, 10, 163, 242, 45, 173, 192, 17, 230, 86, 120, 156, 138, 106, 18, 2, 17, 0, 0, 0, 19, 1, 241, 229, 127, 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