Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a473bc9601d7e5f59eb40dfcd88e95724d454575e6911759a759018b613bcfa1

Tx prefix hash: 988bab16d1b7ef3a1499c4e883b9988a353e7ea85495cbb4bd6312adf17a092a
Tx public key: 83e1a6f6a39d5462e80efea5ec00c4a7138e1b6c78c3d1c01427ec4699dcda68
Timestamp: 1718448952 Timestamp [UCT]: 2024-06-15 10:55:52 Age [y:d:h:m:s]: 00:291:04:33:23
Block: 1044708 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208076 RingCT/type: yes/0
Extra: 0183e1a6f6a39d5462e80efea5ec00c4a7138e1b6c78c3d1c01427ec4699dcda68021100000006cd63fb1b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9127144c8effca2de93be0ed4e4fd895ff0c4b9e79acf808bc1d1f2add6e76b1 0.600000000000 1514089 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": 1044718, "vin": [ { "gen": { "height": 1044708 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9127144c8effca2de93be0ed4e4fd895ff0c4b9e79acf808bc1d1f2add6e76b1" } } ], "extra": [ 1, 131, 225, 166, 246, 163, 157, 84, 98, 232, 14, 254, 165, 236, 0, 196, 167, 19, 142, 27, 108, 120, 195, 209, 192, 20, 39, 236, 70, 153, 220, 218, 104, 2, 17, 0, 0, 0, 6, 205, 99, 251, 27, 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