Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d3add27493802ff06306017c80781a9fc3eacd0fdb5719fa4d7c42b07c03252

Tx prefix hash: 855e6eb0d65d21158b3f0af66ed0f9b889bbc8d2e230083026dd67053ea4798d
Tx public key: e908d2c82c93bcf87c6d10e1c69b1ca377fe895982a338de392225f012c222f7
Timestamp: 1727851461 Timestamp [UCT]: 2024-10-02 06:44:21 Age [y:d:h:m:s]: 00:100:09:17:51
Block: 1122650 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71760 RingCT/type: yes/0
Extra: 01e908d2c82c93bcf87c6d10e1c69b1ca377fe895982a338de392225f012c222f702110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be4411375d6aa2bb39ef4efc76ca846338b15f1bc973abd0e7c4c78d8c733144 0.600000000000 1605131 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": 1122660, "vin": [ { "gen": { "height": 1122650 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be4411375d6aa2bb39ef4efc76ca846338b15f1bc973abd0e7c4c78d8c733144" } } ], "extra": [ 1, 233, 8, 210, 200, 44, 147, 188, 248, 124, 109, 16, 225, 198, 155, 28, 163, 119, 254, 137, 89, 130, 163, 56, 222, 57, 34, 37, 240, 18, 194, 34, 247, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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