Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b988f4a0875e846ae8dababe487162574cd2031e38ed421361352e77d1b5783

Tx prefix hash: 26b7961bc8667ff89bea64c6a34729fceca32bb413fb423f6869b7bcdec11dd6
Tx public key: f33f2e7c8fce2cf3a4029f6ea0a692f3379980b096e5f03d387581c1d94182bf
Timestamp: 1745218458 Timestamp [UCT]: 2025-04-21 06:54:18 Age [y:d:h:m:s]: 00:261:23:04:42
Block: 1266107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185026 RingCT/type: yes/0
Extra: 01f33f2e7c8fce2cf3a4029f6ea0a692f3379980b096e5f03d387581c1d94182bf02110000000adbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ec50245c4031f41099cf68e8e2096733d13a640c8385eba8714a084dcc8b245 0.600000000000 1753322 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": 1266117, "vin": [ { "gen": { "height": 1266107 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ec50245c4031f41099cf68e8e2096733d13a640c8385eba8714a084dcc8b245" } } ], "extra": [ 1, 243, 63, 46, 124, 143, 206, 44, 243, 164, 2, 159, 110, 160, 166, 146, 243, 55, 153, 128, 176, 150, 229, 240, 61, 56, 117, 129, 193, 217, 65, 130, 191, 2, 17, 0, 0, 0, 10, 219, 181, 113, 193, 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