Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e9bf239c2b74b3a6279189e961c25743d8e20f6a17402ca71c3975ab2e9a141

Tx prefix hash: 308b6f4475b0d354963f68a58d311410bfd1270a508a2c51d8d42753b3aa1958
Tx public key: ba257c1372ae01ecd5e89e947d29fc86fb1ff78672dda9e3f5f7f6409d9372e6
Timestamp: 1681281385 Timestamp [UCT]: 2023-04-12 06:36:25 Age [y:d:h:m:s]: 01:352:05:54:56
Block: 736788 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 513048 RingCT/type: yes/0
Extra: 01ba257c1372ae01ecd5e89e947d29fc86fb1ff78672dda9e3f5f7f6409d9372e6021100000001faf35c9c000000000000000000

1 output(s) for total of 2.221855052000 dcy

stealth address amount amount idx
00: 1ddff808b099cb043022cec3a070820f74c81f1f6470223b01c42d4d50a18cc4 2.221855052000 1183259 of 0

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": 736798, "vin": [ { "gen": { "height": 736788 } } ], "vout": [ { "amount": 2221855052, "target": { "key": "1ddff808b099cb043022cec3a070820f74c81f1f6470223b01c42d4d50a18cc4" } } ], "extra": [ 1, 186, 37, 124, 19, 114, 174, 1, 236, 213, 232, 158, 148, 125, 41, 252, 134, 251, 31, 247, 134, 114, 221, 169, 227, 245, 247, 246, 64, 157, 147, 114, 230, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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