Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8286161c86258ae1f6e2b11d1a0abb1806cf4e300b8901eea8da24f4e75d3e74

Tx prefix hash: a6f068144680c148cec06cc2f47c0827665341ea72ba4a57be8683d4bd15d5e3
Tx public key: a52fbec49806c69f522b57858a808425ec8ef632f650aacfe4b0cbb71051db94
Timestamp: 1711384252 Timestamp [UCT]: 2024-03-25 16:30:52 Age [y:d:h:m:s]: 01:035:21:30:22
Block: 986152 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286615 RingCT/type: yes/0
Extra: 01a52fbec49806c69f522b57858a808425ec8ef632f650aacfe4b0cbb71051db940211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dfefdcbdc6bf9c9d810e5020eb324b06a3d6ff7d8e55bf4b6b3eab53e2bad4c7 0.600000000000 1446379 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": 986162, "vin": [ { "gen": { "height": 986152 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dfefdcbdc6bf9c9d810e5020eb324b06a3d6ff7d8e55bf4b6b3eab53e2bad4c7" } } ], "extra": [ 1, 165, 47, 190, 196, 152, 6, 198, 159, 82, 43, 87, 133, 138, 128, 132, 37, 236, 142, 246, 50, 246, 80, 170, 207, 228, 176, 203, 183, 16, 81, 219, 148, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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