Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2deea5e6a82e4a9072c1147a09eb2498d057c7e6a871032efc442c1a8cbbc4a1

Tx prefix hash: 533cb3076fff0086d5b72d98f819feafd0e471fdfc041b0ffc6c48d6e2f5d5a3
Tx public key: a3fb65e78ecae9c8c93bdff99eff1e71080ea68019852f315c51fd443e27fdf8
Timestamp: 1730663045 Timestamp [UCT]: 2024-11-03 19:44:05 Age [y:d:h:m:s]: 00:206:11:58:46
Block: 1145877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147465 RingCT/type: yes/0
Extra: 01a3fb65e78ecae9c8c93bdff99eff1e71080ea68019852f315c51fd443e27fdf80211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a7ce0ef14516a74713ac7bd31d77bd41f8a0c1dc613a4cbad8a807f77695c3f 0.600000000000 1630404 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": 1145887, "vin": [ { "gen": { "height": 1145877 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a7ce0ef14516a74713ac7bd31d77bd41f8a0c1dc613a4cbad8a807f77695c3f" } } ], "extra": [ 1, 163, 251, 101, 231, 142, 202, 233, 200, 201, 59, 223, 249, 158, 255, 30, 113, 8, 14, 166, 128, 25, 133, 47, 49, 92, 81, 253, 68, 62, 39, 253, 248, 2, 17, 0, 0, 0, 6, 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