Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae45499c6724f2efd11646d03bdae3689ac9761189f48fd52daa49ff37c51b7f

Tx prefix hash: c34a4e52efd62b1bfe6b920969be6e28cd2117cde036e777234848f1519ae5ea
Tx public key: fa0079d6475496e8bfba55d2cf6fb7b4d03fcb56a97b5ecc0645d0a4f2dece90
Timestamp: 1717110522 Timestamp [UCT]: 2024-05-30 23:08:42 Age [y:d:h:m:s]: 00:239:00:10:36
Block: 1033595 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171007 RingCT/type: yes/0
Extra: 01fa0079d6475496e8bfba55d2cf6fb7b4d03fcb56a97b5ecc0645d0a4f2dece9002110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a97908f2aed850d58c87673c011a68334fb1129fb474fecd1eca2aa91a98e13 0.600000000000 1502066 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": 1033605, "vin": [ { "gen": { "height": 1033595 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a97908f2aed850d58c87673c011a68334fb1129fb474fecd1eca2aa91a98e13" } } ], "extra": [ 1, 250, 0, 121, 214, 71, 84, 150, 232, 191, 186, 85, 210, 207, 111, 183, 180, 208, 63, 203, 86, 169, 123, 94, 204, 6, 69, 208, 164, 242, 222, 206, 144, 2, 17, 0, 0, 0, 1, 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