Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf9fbaaf7a188cded2ad3f6591ebbf7249642162721378c4b07ac8c46d178e8d

Tx prefix hash: a7a59ebf9e11fb6037d7022a03655729bd236c0ce3efc1ef7ab0d2d2daf1bf00
Tx public key: a1eeb6907ae343af9895466549004262bcf256f4bddffeca40d77f19d8186048
Timestamp: 1708219873 Timestamp [UCT]: 2024-02-18 01:31:13 Age [y:d:h:m:s]: 01:046:00:26:30
Block: 959883 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293916 RingCT/type: yes/0
Extra: 01a1eeb6907ae343af9895466549004262bcf256f4bddffeca40d77f19d81860480211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 62d70ba68dd3fdca5046b2cf8c2d8880fd17449e89698c8a80b5f74a088d96e8 0.600000000000 1419442 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": 959893, "vin": [ { "gen": { "height": 959883 } } ], "vout": [ { "amount": 600000000, "target": { "key": "62d70ba68dd3fdca5046b2cf8c2d8880fd17449e89698c8a80b5f74a088d96e8" } } ], "extra": [ 1, 161, 238, 182, 144, 122, 227, 67, 175, 152, 149, 70, 101, 73, 0, 66, 98, 188, 242, 86, 244, 189, 223, 254, 202, 64, 215, 127, 25, 216, 24, 96, 72, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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