Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1f1b9e3fa33853fa7bd34f9dfd7ea5cf9b080eb47edd9ddba8de105abb3e377

Tx prefix hash: 48be7a5c05c16999c62987eb1936404fbe517b5e3b07115981d2e1b2fea51644
Tx public key: bfdf87ed260a0232172971003fef2a368724b0b59f3d4ddcb9e2724ded968606
Timestamp: 1661306484 Timestamp [UCT]: 2022-08-24 02:01:24 Age [y:d:h:m:s]: 02:225:16:01:44
Block: 572465 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 682541 RingCT/type: yes/0
Extra: 01bfdf87ed260a0232172971003fef2a368724b0b59f3d4ddcb9e2724ded968606021100000002f7dd2130000000000000000000

1 output(s) for total of 7.783696843000 dcy

stealth address amount amount idx
00: 1a8a8a5cba173a62ee5d80e8baa3726f1fe1bf03b27ec4c37250a6bf5c28fc45 7.783696843000 1005715 of 0

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": 572475, "vin": [ { "gen": { "height": 572465 } } ], "vout": [ { "amount": 7783696843, "target": { "key": "1a8a8a5cba173a62ee5d80e8baa3726f1fe1bf03b27ec4c37250a6bf5c28fc45" } } ], "extra": [ 1, 191, 223, 135, 237, 38, 10, 2, 50, 23, 41, 113, 0, 63, 239, 42, 54, 135, 36, 176, 181, 159, 61, 77, 220, 185, 226, 114, 77, 237, 150, 134, 6, 2, 17, 0, 0, 0, 2, 247, 221, 33, 48, 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