Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69ec6b36cabc8aec82a75052907966fcab8d9a4be066968b2e91e27ad73afa33

Tx prefix hash: 66c6957a2abfcbb17272f8ae0f716f59306cf7232cf2f2cfff29cd5580814502
Tx public key: 3a46af499bf34ff6f87c5cc9182c2a143a5689dc5030e4846c047c513a2c9a4a
Timestamp: 1721148442 Timestamp [UCT]: 2024-07-16 16:47:22 Age [y:d:h:m:s]: 00:304:15:12:00
Block: 1067096 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217653 RingCT/type: yes/0
Extra: 013a46af499bf34ff6f87c5cc9182c2a143a5689dc5030e4846c047c513a2c9a4a021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25d038f5ba9d9809a5115f8c12a644829106e7e2d87158f76d9af26815543533 0.600000000000 1537815 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": 1067106, "vin": [ { "gen": { "height": 1067096 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25d038f5ba9d9809a5115f8c12a644829106e7e2d87158f76d9af26815543533" } } ], "extra": [ 1, 58, 70, 175, 73, 155, 243, 79, 246, 248, 124, 92, 201, 24, 44, 42, 20, 58, 86, 137, 220, 80, 48, 228, 132, 108, 4, 124, 81, 58, 44, 154, 74, 2, 17, 0, 0, 0, 5, 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