Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e09ddd4a496544964396062ce6a4982e9ad3e5b3ed61188460891b2466e3707

Tx prefix hash: 75ad273e66a7c70e1c644c48fd6d57c143186afb81903f49d5a34d41b1a59618
Tx public key: df89436d29388ad9541cddd0a7aab85937c0c67d1c0ca022b5487f63101ca713
Timestamp: 1702370927 Timestamp [UCT]: 2023-12-12 08:48:47 Age [y:d:h:m:s]: 01:144:19:51:16
Block: 911415 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364641 RingCT/type: yes/0
Extra: 01df89436d29388ad9541cddd0a7aab85937c0c67d1c0ca022b5487f63101ca71302110000000d75e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e93e5e8843e5d159a654a8d46f708d894a4c078529c58a2c27139b59a18bea80 0.600000000000 1368617 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": 911425, "vin": [ { "gen": { "height": 911415 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e93e5e8843e5d159a654a8d46f708d894a4c078529c58a2c27139b59a18bea80" } } ], "extra": [ 1, 223, 137, 67, 109, 41, 56, 138, 217, 84, 28, 221, 208, 167, 170, 184, 89, 55, 192, 198, 125, 28, 12, 160, 34, 181, 72, 127, 99, 16, 28, 167, 19, 2, 17, 0, 0, 0, 13, 117, 227, 240, 233, 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