Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 818e53530c9d2bb5cddf66ac42971eb7730f13707177ce2b097f8de62eb5d746

Tx prefix hash: df8f5ffd841d77518254e615a5e34e257a505eba8c74e3199a53295731de4215
Tx public key: 2213057b325a9399039f3c44e49554c8297b79ad7891dac5ff1331e9ad250c72
Timestamp: 1683712200 Timestamp [UCT]: 2023-05-10 09:50:00 Age [y:d:h:m:s]: 01:342:12:23:48
Block: 756969 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 506029 RingCT/type: yes/0
Extra: 012213057b325a9399039f3c44e49554c8297b79ad7891dac5ff1331e9ad250c72021100000004faf35c9c000000000000000000

1 output(s) for total of 1.904792459000 dcy

stealth address amount amount idx
00: d8c743b878e9c7fdd9fdfbfd0ac4b4f798fb54b4ff3a5189035e210a4f829742 1.904792459000 1205374 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": 756979, "vin": [ { "gen": { "height": 756969 } } ], "vout": [ { "amount": 1904792459, "target": { "key": "d8c743b878e9c7fdd9fdfbfd0ac4b4f798fb54b4ff3a5189035e210a4f829742" } } ], "extra": [ 1, 34, 19, 5, 123, 50, 90, 147, 153, 3, 159, 60, 68, 228, 149, 84, 200, 41, 123, 121, 173, 120, 145, 218, 197, 255, 19, 49, 233, 173, 37, 12, 114, 2, 17, 0, 0, 0, 4, 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