Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b6d5f2d181f3d616938042073e1662dccf799274fd985b368ae5c78f9fb46e5

Tx prefix hash: 9370a86d0a3a7d3b805a1172b6e3399048bb19f036a719fdf49db4dc11cc8a02
Tx public key: fb58c14de782fcc88ead25415117961e764dc77be8bb36645b4ecac69051f9ff
Timestamp: 1731993399 Timestamp [UCT]: 2024-11-19 05:16:39 Age [y:d:h:m:s]: 00:141:19:51:43
Block: 1156894 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101183 RingCT/type: yes/0
Extra: 01fb58c14de782fcc88ead25415117961e764dc77be8bb36645b4ecac69051f9ff0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 499f2f063496a8f82e22c2dbdcc2d7a484bfc301db5c978b482475e6cbb4bf40 0.600000000000 1642517 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": 1156904, "vin": [ { "gen": { "height": 1156894 } } ], "vout": [ { "amount": 600000000, "target": { "key": "499f2f063496a8f82e22c2dbdcc2d7a484bfc301db5c978b482475e6cbb4bf40" } } ], "extra": [ 1, 251, 88, 193, 77, 231, 130, 252, 200, 142, 173, 37, 65, 81, 23, 150, 30, 118, 77, 199, 123, 232, 187, 54, 100, 91, 78, 202, 198, 144, 81, 249, 255, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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