Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81b94c56c4d774dec83f9f56403ad23bc788d3fbd86c1e1aab72d48b0208371a

Tx prefix hash: 347b197db27abae47f8c04fefd28d831dcf54008de3af627f5f401046c2ad377
Tx public key: 736263ed7b01caccaa4e4da72b10a5b1bb2ed73ad1190bdf64cc763f287371f8
Timestamp: 1749933117 Timestamp [UCT]: 2025-06-14 20:31:57 Age [y:d:h:m:s]: 00:158:21:12:28
Block: 1305062 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111327 RingCT/type: yes/0
Extra: 01736263ed7b01caccaa4e4da72b10a5b1bb2ed73ad1190bdf64cc763f287371f802110000000443846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae32e253e8703404c819873f33fba1fd74c0e88aa6e7a6b6378e00b241a84ac2 0.600000000000 1792661 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": 1305072, "vin": [ { "gen": { "height": 1305062 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae32e253e8703404c819873f33fba1fd74c0e88aa6e7a6b6378e00b241a84ac2" } } ], "extra": [ 1, 115, 98, 99, 237, 123, 1, 202, 204, 170, 78, 77, 167, 43, 16, 165, 177, 187, 46, 215, 58, 209, 25, 11, 223, 100, 204, 118, 63, 40, 115, 113, 248, 2, 17, 0, 0, 0, 4, 67, 132, 109, 102, 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