Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 800570fdf0ad0001ca35271524fddce761658a57ceba683d79ed3ae067464322

Tx prefix hash: c15087b3435abaeea33c809f9528676a78ba23b942ddd38a4ae55f530f9d630f
Tx public key: f1e0f20c2a0ee1e6a1b4618087f300364d40d7f6cb9d276b98fcf0e93e039ba5
Timestamp: 1730777945 Timestamp [UCT]: 2024-11-05 03:39:05 Age [y:d:h:m:s]: 00:227:09:06:49
Block: 1146821 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162228 RingCT/type: yes/0
Extra: 01f1e0f20c2a0ee1e6a1b4618087f300364d40d7f6cb9d276b98fcf0e93e039ba5021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a4a18219b2ca9971c2b66fb7a18b18c64af31ab258f54d0941ab2cedc4e5858 0.600000000000 1631512 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": 1146831, "vin": [ { "gen": { "height": 1146821 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a4a18219b2ca9971c2b66fb7a18b18c64af31ab258f54d0941ab2cedc4e5858" } } ], "extra": [ 1, 241, 224, 242, 12, 42, 14, 225, 230, 161, 180, 97, 128, 135, 243, 0, 54, 77, 64, 215, 246, 203, 157, 39, 107, 152, 252, 240, 233, 62, 3, 155, 165, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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