Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5c0ecaa47312dde4b870716b142a894b1f25df675555ae2e99a2fae9276b135

Tx prefix hash: cf05b21fc0c128bb011950b2d7aa1874880f9b24d03eb3ffd9c89993d57849d1
Tx public key: 8e8e77f9f6bc83b70c0d5c6762c8062c50d2f08e46f68a252260507284f89743
Timestamp: 1630864034 Timestamp [UCT]: 2021-09-05 17:47:14 Age [y:d:h:m:s]: 03:122:10:32:34
Block: 328041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 862461 RingCT/type: yes/0
Extra: 018e8e77f9f6bc83b70c0d5c6762c8062c50d2f08e46f68a252260507284f897430211000000110254cd56000000000000000000

1 output(s) for total of 50.241713206000 dcy

stealth address amount amount idx
00: 7d1d36c8220bf7635e43a284455cd852c9c6c1b1f140ea31806f643d28fda6f2 50.241713206000 679126 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": 328051, "vin": [ { "gen": { "height": 328041 } } ], "vout": [ { "amount": 50241713206, "target": { "key": "7d1d36c8220bf7635e43a284455cd852c9c6c1b1f140ea31806f643d28fda6f2" } } ], "extra": [ 1, 142, 142, 119, 249, 246, 188, 131, 183, 12, 13, 92, 103, 98, 200, 6, 44, 80, 210, 240, 142, 70, 246, 138, 37, 34, 96, 80, 114, 132, 248, 151, 67, 2, 17, 0, 0, 0, 17, 2, 84, 205, 86, 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