Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 803ed09a433e40b58e87b34418e16b3275e47c9a621bdecbbf7a7d45cba74925

Tx prefix hash: 526a11c845bd667b5a17ea155b318eee88e5094a25fba1b81ef6f25119380a77
Tx public key: 6eb3a8424f4f68e14a5400d0e8ccb70079963829b23c86d0f03123d4748b948f
Timestamp: 1720053621 Timestamp [UCT]: 2024-07-04 00:40:21 Age [y:d:h:m:s]: 00:272:14:30:12
Block: 1057991 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194785 RingCT/type: yes/0
Extra: 016eb3a8424f4f68e14a5400d0e8ccb70079963829b23c86d0f03123d4748b948f0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d7bd09ce8b4fabc5a450d47e91ab5158b1ebd15832b8d649de7160f5670d5509 0.600000000000 1528434 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": 1058001, "vin": [ { "gen": { "height": 1057991 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d7bd09ce8b4fabc5a450d47e91ab5158b1ebd15832b8d649de7160f5670d5509" } } ], "extra": [ 1, 110, 179, 168, 66, 79, 79, 104, 225, 74, 84, 0, 208, 232, 204, 183, 0, 121, 150, 56, 41, 178, 60, 134, 208, 240, 49, 35, 212, 116, 139, 148, 143, 2, 17, 0, 0, 0, 2, 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