Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf01c1de3b397348ba51d13495b87aa9eacab87b798f8dfd4fbd563eda7fdc32

Tx prefix hash: 5eeec62fdde3a5a1178641057f909beac2de497f50894e649506fa488ca20f33
Tx public key: dc0dfc7e114bf88cbf902c62e57e71d6d3e67bdb146d808949f9e2c89cde1ed2
Timestamp: 1736020866 Timestamp [UCT]: 2025-01-04 20:01:06 Age [y:d:h:m:s]: 00:346:01:59:38
Block: 1190247 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244889 RingCT/type: yes/0
Extra: 01dc0dfc7e114bf88cbf902c62e57e71d6d3e67bdb146d808949f9e2c89cde1ed202110000000b007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46740aaf88e1b5bad03f2a512fb858d4ac35b61e57b4796e22c6672a5d5dd185 0.600000000000 1676762 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": 1190257, "vin": [ { "gen": { "height": 1190247 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46740aaf88e1b5bad03f2a512fb858d4ac35b61e57b4796e22c6672a5d5dd185" } } ], "extra": [ 1, 220, 13, 252, 126, 17, 75, 248, 140, 191, 144, 44, 98, 229, 126, 113, 214, 211, 230, 123, 219, 20, 109, 128, 137, 73, 249, 226, 200, 156, 222, 30, 210, 2, 17, 0, 0, 0, 11, 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