Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6ab60b0a61a83978117c23c10f42d2ffa21627010b4ff0a40ffefb1ef8dd458

Tx prefix hash: 241a965f0d74d0c462545689d96d1697bf4e07c7d2bc442d6d8c8fdd10a815d7
Tx public key: 1fba579fec629287ca44e6778fb6f36dd1cf19cfa0b2d129ec75d38b4d24058a
Timestamp: 1748147505 Timestamp [UCT]: 2025-05-25 04:31:45 Age [y:d:h:m:s]: 00:252:06:16:24
Block: 1290376 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177898 RingCT/type: yes/0
Extra: 011fba579fec629287ca44e6778fb6f36dd1cf19cfa0b2d129ec75d38b4d24058a021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b1ffdfe860a57f0bc9cc546ca871e0156ab9fed2f634983a72e9f64a5144d78 0.600000000000 1777845 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": 1290386, "vin": [ { "gen": { "height": 1290376 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b1ffdfe860a57f0bc9cc546ca871e0156ab9fed2f634983a72e9f64a5144d78" } } ], "extra": [ 1, 31, 186, 87, 159, 236, 98, 146, 135, 202, 68, 230, 119, 143, 182, 243, 109, 209, 207, 25, 207, 160, 178, 209, 41, 236, 117, 211, 139, 77, 36, 5, 138, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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