Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d3ecc5d565c9fe89dbf3f78f55aa1b07ba4cdcaef1edc37d5aa0957aa8d63e5

Tx prefix hash: 3839e51ccb78d5807e3e66b0a76aeff448320336312db73d5d33b7f212e36c61
Tx public key: b2c5517aa05d35904920d5365359e52e22afad465f21b86c63a858eadbb73047
Timestamp: 1713094708 Timestamp [UCT]: 2024-04-14 11:38:28 Age [y:d:h:m:s]: 00:338:23:25:25
Block: 1000285 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242377 RingCT/type: yes/0
Extra: 01b2c5517aa05d35904920d5365359e52e22afad465f21b86c63a858eadbb7304702110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 12d564529d5d67b9f68846c089315b9c04f2b3d7fa25b44063dfb2630f3f86ae 0.600000000000 1460781 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": 1000295, "vin": [ { "gen": { "height": 1000285 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12d564529d5d67b9f68846c089315b9c04f2b3d7fa25b44063dfb2630f3f86ae" } } ], "extra": [ 1, 178, 197, 81, 122, 160, 93, 53, 144, 73, 32, 213, 54, 83, 89, 229, 46, 34, 175, 173, 70, 95, 33, 184, 108, 99, 168, 88, 234, 219, 183, 48, 71, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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