Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e11bbe5e7e318eac11bd62e1584c0325ad690778a681cc1355bba0c591bedb0

Tx prefix hash: 627764ce06d88cfd5ec780bdbd67d222e1c1f64c983a10f54b6ee27e218ce631
Tx public key: 1134a5c152d8ee4c7bb1f2131366521ebd864b5f9425052e6944d7fd3e1973d5
Timestamp: 1762532239 Timestamp [UCT]: 2025-11-07 16:17:19 Age [y:d:h:m:s]: 00:013:06:10:40
Block: 1407044 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9486 RingCT/type: yes/0
Extra: 011134a5c152d8ee4c7bb1f2131366521ebd864b5f9425052e6944d7fd3e1973d50211000000085dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6a067058b1fbbe3a95507cb0d6ca625287e234a0ae568eb3e2b50f3e49d6436 0.600000000000 1895451 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": 1407054, "vin": [ { "gen": { "height": 1407044 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6a067058b1fbbe3a95507cb0d6ca625287e234a0ae568eb3e2b50f3e49d6436" } } ], "extra": [ 1, 17, 52, 165, 193, 82, 216, 238, 76, 123, 177, 242, 19, 19, 102, 82, 30, 189, 134, 75, 95, 148, 37, 5, 46, 105, 68, 215, 253, 62, 25, 115, 213, 2, 17, 0, 0, 0, 8, 93, 251, 190, 42, 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