Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7ac6bedbcc097bb82193601a568a5556be2ded664e212b1e8fd3b5726e75d82

Tx prefix hash: adb73036837f55397357b4f2377bb0e1fde93e7758c8f5f8a421ccf16237d111
Tx public key: 1aa1c2e8f6a5ad461d8c0515d778de8d7ffe4d6659b3f2d6015a2e1e92f90792
Timestamp: 1741214950 Timestamp [UCT]: 2025-03-05 22:49:10 Age [y:d:h:m:s]: 00:013:20:30:14
Block: 1232984 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9917 RingCT/type: yes/0
Extra: 011aa1c2e8f6a5ad461d8c0515d778de8d7ffe4d6659b3f2d6015a2e1e92f907920211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f5b821fb6fb8deb1f9ce906aac7bf3d5bb3d87a5b3ad6b39ab8c3d5d01cc1a3 0.600000000000 1719901 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": 1232994, "vin": [ { "gen": { "height": 1232984 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f5b821fb6fb8deb1f9ce906aac7bf3d5bb3d87a5b3ad6b39ab8c3d5d01cc1a3" } } ], "extra": [ 1, 26, 161, 194, 232, 246, 165, 173, 70, 29, 140, 5, 21, 215, 120, 222, 141, 127, 254, 77, 102, 89, 179, 242, 214, 1, 90, 46, 30, 146, 249, 7, 146, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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