Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bf37e4ba301d0995d13d7411fa5f64c5f829d589b7302333c0e965e6765290f

Tx prefix hash: 55ac84c8fb10bc7abee647a8c48d3b3c8b49a8b5f152dcfe5040e3fe4df97bd1
Tx public key: ba416de33e797a9829615aed05be2090c554c245da826364a9722a7d239b97c2
Timestamp: 1725395882 Timestamp [UCT]: 2024-09-03 20:38:02 Age [y:d:h:m:s]: 00:212:12:48:38
Block: 1102295 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151742 RingCT/type: yes/0
Extra: 01ba416de33e797a9829615aed05be2090c554c245da826364a9722a7d239b97c202110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 11c2d71261c8f6dbc2fb4d714bc62d9b8a8484b8f9c78bb81ebbc7977449ec90 0.600000000000 1578674 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": 1102305, "vin": [ { "gen": { "height": 1102295 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11c2d71261c8f6dbc2fb4d714bc62d9b8a8484b8f9c78bb81ebbc7977449ec90" } } ], "extra": [ 1, 186, 65, 109, 227, 62, 121, 122, 152, 41, 97, 90, 237, 5, 190, 32, 144, 197, 84, 194, 69, 218, 130, 99, 100, 169, 114, 42, 125, 35, 155, 151, 194, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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