Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 817a60fc72aff2a9f57ceb04f0c3e21b6cdfcc4d740f340bb385d2cfd9807c64

Tx prefix hash: 747bee73e2cc5638e2364e62f5fbdea8f6603beb036ae9dbf4a76ef4cef9035a
Tx public key: d987ae1a99788264e3b5f77e45458c2c4b9d2a33b029a685a1de99f9c75573e6
Timestamp: 1696723006 Timestamp [UCT]: 2023-10-07 23:56:46 Age [y:d:h:m:s]: 01:011:13:22:34
Block: 864783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 269526 RingCT/type: yes/0
Extra: 01d987ae1a99788264e3b5f77e45458c2c4b9d2a33b029a685a1de99f9c75573e602110000000433af99f4000000000000000000

1 output(s) for total of 0.836787083000 dcy

stealth address amount amount idx
00: 5ea040930f80a325906f63fee28ce0530e94f0c592679b0b873a453bd39a34dc 0.836787083000 1319303 of 0

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": 864793, "vin": [ { "gen": { "height": 864783 } } ], "vout": [ { "amount": 836787083, "target": { "key": "5ea040930f80a325906f63fee28ce0530e94f0c592679b0b873a453bd39a34dc" } } ], "extra": [ 1, 217, 135, 174, 26, 153, 120, 130, 100, 227, 181, 247, 126, 69, 69, 140, 44, 75, 157, 42, 51, 176, 41, 166, 133, 161, 222, 153, 249, 199, 85, 115, 230, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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