Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c6cce289dcc47322276441be7cd3d1e67dc6f99cbe4930f592ff068bffdc4e7

Tx prefix hash: 51cd0e1c5c6df5db201a2c53e57ba96c008f4fd193e96841001b8506000feb72
Tx public key: 8f629922edfc4f4537c941ad10770820adbc929fdc6dffc890dcb1526b4edc0d
Timestamp: 1732263190 Timestamp [UCT]: 2024-11-22 08:13:10 Age [y:d:h:m:s]: 00:001:19:01:08
Block: 1159124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1286 RingCT/type: yes/0
Extra: 018f629922edfc4f4537c941ad10770820adbc929fdc6dffc890dcb1526b4edc0d021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8ac0d7d77a2a220217a16072919d77affccd1ebc664cf01ebc6c9accb886aca3 0.600000000000 1644755 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": 1159134, "vin": [ { "gen": { "height": 1159124 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ac0d7d77a2a220217a16072919d77affccd1ebc664cf01ebc6c9accb886aca3" } } ], "extra": [ 1, 143, 98, 153, 34, 237, 252, 79, 69, 55, 201, 65, 173, 16, 119, 8, 32, 173, 188, 146, 159, 220, 109, 255, 200, 144, 220, 177, 82, 107, 78, 220, 13, 2, 17, 0, 0, 0, 6, 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