Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3261886162cf316316d8f728b7acc9e7f545f346d8b9e0068054ced58febfe76

Tx prefix hash: 9596311e35a200434f04755911acad6d7a1e1c22235dfcbbe6f89b65e5d3341a
Tx public key: 73ca5ce59ffc9ec3b5413a3c567c237b38f82acc2525d8d49f24888b5edfe00a
Timestamp: 1737497402 Timestamp [UCT]: 2025-01-21 22:10:02 Age [y:d:h:m:s]: 00:147:14:26:45
Block: 1202414 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105245 RingCT/type: yes/0
Extra: 0173ca5ce59ffc9ec3b5413a3c567c237b38f82acc2525d8d49f24888b5edfe00a021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3a1d7780604fa6a4beff58d275ea6ae9c0bce1e58740652728a9e58126f27d6 0.600000000000 1689077 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": 1202424, "vin": [ { "gen": { "height": 1202414 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3a1d7780604fa6a4beff58d275ea6ae9c0bce1e58740652728a9e58126f27d6" } } ], "extra": [ 1, 115, 202, 92, 229, 159, 252, 158, 195, 181, 65, 58, 60, 86, 124, 35, 123, 56, 248, 42, 204, 37, 37, 216, 212, 159, 36, 136, 139, 94, 223, 224, 10, 2, 17, 0, 0, 0, 2, 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