Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ed0dc29f2739bb6335d42e4d361568b63d6fb0337a2f8cd3840402dad24ea4a

Tx prefix hash: f773b449da32d16edbc2b823b366689ddab29c613c110639a95ac6d3c8cd0bc2
Tx public key: 22cf50f3f07e7c1176f9a5fe392122f3b8fb0ab1b16bd8b57bd760253dd06f83
Timestamp: 1732735201 Timestamp [UCT]: 2024-11-27 19:20:01 Age [y:d:h:m:s]: 00:124:01:36:28
Block: 1163034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88479 RingCT/type: yes/0
Extra: 0122cf50f3f07e7c1176f9a5fe392122f3b8fb0ab1b16bd8b57bd760253dd06f83021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ca1a91da8e12e51508139527b717dd44d6f4befdbcd6701a1ba5f9678e2d7750 0.600000000000 1648697 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": 1163044, "vin": [ { "gen": { "height": 1163034 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ca1a91da8e12e51508139527b717dd44d6f4befdbcd6701a1ba5f9678e2d7750" } } ], "extra": [ 1, 34, 207, 80, 243, 240, 126, 124, 17, 118, 249, 165, 254, 57, 33, 34, 243, 184, 251, 10, 177, 177, 107, 216, 181, 123, 215, 96, 37, 61, 208, 111, 131, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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