Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 324a5b3bf1213a3ee5d18c5a4e9025e54c5177543af9e566ebdd1c1d86382928

Tx prefix hash: 8c58f51992f25ebe0c71132f3b0ba8b9236bd7d4c2d59f45e4407ab841b322a6
Tx public key: b97fb101f4f2c285672335841737713432a95c4edc96d8df80a7c3970588b863
Timestamp: 1710301671 Timestamp [UCT]: 2024-03-13 03:47:51 Age [y:d:h:m:s]: 01:237:14:28:50
Block: 977166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 428500 RingCT/type: yes/0
Extra: 01b97fb101f4f2c285672335841737713432a95c4edc96d8df80a7c3970588b86302110000000b52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2343b6b12837f57a3e13ad71f8ac7aa57f76c762ccf074651b87fddff1ab33f2 0.600000000000 1437167 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": 977176, "vin": [ { "gen": { "height": 977166 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2343b6b12837f57a3e13ad71f8ac7aa57f76c762ccf074651b87fddff1ab33f2" } } ], "extra": [ 1, 185, 127, 177, 1, 244, 242, 194, 133, 103, 35, 53, 132, 23, 55, 113, 52, 50, 169, 92, 78, 220, 150, 216, 223, 128, 167, 195, 151, 5, 136, 184, 99, 2, 17, 0, 0, 0, 11, 82, 212, 126, 148, 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