Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9633536160a6a48b0e3ac5777d391ec7f21b98d0a8ca6bacd109d98831c92e73

Tx prefix hash: ca36693de64a4b4696b0a6192befede2bf657654bcf0d8a1b70abcb5e433f57a
Tx public key: 8e14f92d0f35ffb145f0bd3f9959d376a2108ada368063bc7fc64142a8fca2de
Timestamp: 1729473671 Timestamp [UCT]: 2024-10-21 01:21:11 Age [y:d:h:m:s]: 00:158:05:38:43
Block: 1136063 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112883 RingCT/type: yes/0
Extra: 018e14f92d0f35ffb145f0bd3f9959d376a2108ada368063bc7fc64142a8fca2de0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c65a22eeb28e8ceb6e64f085f5e00564792f9eec0ffb655c6c06e0584f4d03d 0.600000000000 1619406 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": 1136073, "vin": [ { "gen": { "height": 1136063 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c65a22eeb28e8ceb6e64f085f5e00564792f9eec0ffb655c6c06e0584f4d03d" } } ], "extra": [ 1, 142, 20, 249, 45, 15, 53, 255, 177, 69, 240, 189, 63, 153, 89, 211, 118, 162, 16, 138, 218, 54, 128, 99, 188, 127, 198, 65, 66, 168, 252, 162, 222, 2, 17, 0, 0, 0, 1, 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