Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b1eaa523d7f1523607b054f93324d65096648c12dfc3c52c233e86e81b4746d

Tx prefix hash: 6a0a82f0231e37860d559949a66ec280c6679f8af1e2f3cb7aa878129ef6bc89
Tx public key: dbcb964f4058a961aa82956adecbbed81cf419c3380a7e997dfb15016b994c57
Timestamp: 1715324307 Timestamp [UCT]: 2024-05-10 06:58:27 Age [y:d:h:m:s]: 00:230:09:57:40
Block: 1018795 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164913 RingCT/type: yes/0
Extra: 01dbcb964f4058a961aa82956adecbbed81cf419c3380a7e997dfb15016b994c5702110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc93f7deb5f945742773d48ca990233e08d37611f360a7fe81f83d898f6ad9b6 0.600000000000 1482590 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": 1018805, "vin": [ { "gen": { "height": 1018795 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc93f7deb5f945742773d48ca990233e08d37611f360a7fe81f83d898f6ad9b6" } } ], "extra": [ 1, 219, 203, 150, 79, 64, 88, 169, 97, 170, 130, 149, 106, 222, 203, 190, 216, 28, 244, 25, 195, 56, 10, 126, 153, 125, 251, 21, 1, 107, 153, 76, 87, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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