Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0f21826089283fc4f30b1936e95293e421631925dce5d8cb886f04ac97ca6b2

Tx prefix hash: 89b3c212872d3a448776d328529a1c74724a629cfea37ac95676fc703d0d1ff0
Tx public key: 68480b0fb14eef3e5d645e60630c62f916a823da063e5c05bea0bcf6932b8fe5
Timestamp: 1637601473 Timestamp [UCT]: 2021-11-22 17:17:53 Age [y:d:h:m:s]: 03:155:23:23:30
Block: 379824 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 890169 RingCT/type: yes/0
Extra: 0168480b0fb14eef3e5d645e60630c62f916a823da063e5c05bea0bcf6932b8fe5021100000001e9564d6f000000000000000000

1 output(s) for total of 33.844320301000 dcy

stealth address amount amount idx
00: bb66f8400175986590dccd82f88a693141fb7416c3f79478483218a122432722 33.844320301000 767636 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": 379834, "vin": [ { "gen": { "height": 379824 } } ], "vout": [ { "amount": 33844320301, "target": { "key": "bb66f8400175986590dccd82f88a693141fb7416c3f79478483218a122432722" } } ], "extra": [ 1, 104, 72, 11, 15, 177, 78, 239, 62, 93, 100, 94, 96, 99, 12, 98, 249, 22, 168, 35, 218, 6, 62, 92, 5, 190, 160, 188, 246, 147, 43, 143, 229, 2, 17, 0, 0, 0, 1, 233, 86, 77, 111, 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