Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb15152398758ad7a3f056ebd7f27f23951f6dcc7272a4167318ab712b356fb2

Tx prefix hash: 82691a013c20fb6b6e91c3a500ed6f0b754589814ecd7e4cb697306a050d290d
Tx public key: f49de7e63be4594ceb8be664d2499f3c0e401ab76a6d896f882ef96a85ebb0e0
Timestamp: 1741874411 Timestamp [UCT]: 2025-03-13 14:00:11 Age [y:d:h:m:s]: 00:252:04:58:09
Block: 1238450 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177980 RingCT/type: yes/0
Extra: 01f49de7e63be4594ceb8be664d2499f3c0e401ab76a6d896f882ef96a85ebb0e002110000000b1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83c5a12632f8cca5a277437f62e0046821cf07bd60b1e815a9d8929075562eb8 0.600000000000 1725409 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": 1238460, "vin": [ { "gen": { "height": 1238450 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83c5a12632f8cca5a277437f62e0046821cf07bd60b1e815a9d8929075562eb8" } } ], "extra": [ 1, 244, 157, 231, 230, 59, 228, 89, 76, 235, 139, 230, 100, 210, 73, 159, 60, 14, 64, 26, 183, 106, 109, 137, 111, 136, 46, 249, 106, 133, 235, 176, 224, 2, 17, 0, 0, 0, 11, 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