Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 792d29ea18c98202a80b946d0210a29f1ee067efe930124a58a0cb7b7a69e374

Tx prefix hash: 8626d3d5a612e6c7c8a710fc44c5b0045d238228a10740fcb50fa31ce72c9375
Tx public key: ddea50e4d599058483b0219a5002050e5b2b1ae9f8852fb2e27734de398f90f2
Timestamp: 1736259957 Timestamp [UCT]: 2025-01-07 14:25:57 Age [y:d:h:m:s]: 00:087:10:08:15
Block: 1192224 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62264 RingCT/type: yes/0
Extra: 01ddea50e4d599058483b0219a5002050e5b2b1ae9f8852fb2e27734de398f90f20211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e717d29ca81505ab2fc45600633e67b9eaae91d5ee89440ebae0f63b6e07a949 0.600000000000 1678773 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": 1192234, "vin": [ { "gen": { "height": 1192224 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e717d29ca81505ab2fc45600633e67b9eaae91d5ee89440ebae0f63b6e07a949" } } ], "extra": [ 1, 221, 234, 80, 228, 213, 153, 5, 132, 131, 176, 33, 154, 80, 2, 5, 14, 91, 43, 26, 233, 248, 133, 47, 178, 226, 119, 52, 222, 57, 143, 144, 242, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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