Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e138d17fa65e6f9828bf3babe10c404f5dc766cce70e1ad772855907d118607

Tx prefix hash: ea5c4cbc28787ee546bbca9076cb22a2340a0e94d827d72825479ac3eeb276b4
Tx public key: ce3c3eaf1d7e42fd7e3b1eefb97c39a115a216bdcd0a61e5726f5500c901eebb
Timestamp: 1737852338 Timestamp [UCT]: 2025-01-26 00:45:38 Age [y:d:h:m:s]: 00:142:18:58:12
Block: 1205358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101794 RingCT/type: yes/0
Extra: 01ce3c3eaf1d7e42fd7e3b1eefb97c39a115a216bdcd0a61e5726f5500c901eebb021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 86a36cd5f233e70c366a57affc34aa20f116b4098f1cb4932a4b08c04af36ed4 0.600000000000 1692055 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": 1205368, "vin": [ { "gen": { "height": 1205358 } } ], "vout": [ { "amount": 600000000, "target": { "key": "86a36cd5f233e70c366a57affc34aa20f116b4098f1cb4932a4b08c04af36ed4" } } ], "extra": [ 1, 206, 60, 62, 175, 29, 126, 66, 253, 126, 59, 30, 239, 185, 124, 57, 161, 21, 162, 22, 189, 205, 10, 97, 229, 114, 111, 85, 0, 201, 1, 238, 187, 2, 17, 0, 0, 0, 2, 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