Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b31e8f4e167f980f0bd8ed4d98812e2109303f5d2b00f58b13ff3af2b722d5e1

Tx prefix hash: 0bc7daf4cf929fb17d0aaa6155b57e0019da61d811b69eb91c4d16a7418ff36a
Tx public key: ed97692386f8d43f265b8b3ce5d86deee49b23b92561034a5633791f663ad5bd
Timestamp: 1715135701 Timestamp [UCT]: 2024-05-08 02:35:01 Age [y:d:h:m:s]: 00:318:05:12:42
Block: 1017227 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227464 RingCT/type: yes/0
Extra: 01ed97692386f8d43f265b8b3ce5d86deee49b23b92561034a5633791f663ad5bd0211000000090011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0b803f1fefdf24642c1e8d121f262ea683c70a6cae93a6fbcad9771c5da4084 0.600000000000 1480996 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": 1017237, "vin": [ { "gen": { "height": 1017227 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0b803f1fefdf24642c1e8d121f262ea683c70a6cae93a6fbcad9771c5da4084" } } ], "extra": [ 1, 237, 151, 105, 35, 134, 248, 212, 63, 38, 91, 139, 60, 229, 216, 109, 238, 228, 155, 35, 185, 37, 97, 3, 74, 86, 51, 121, 31, 102, 58, 213, 189, 2, 17, 0, 0, 0, 9, 0, 17, 5, 91, 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