Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f4f5980cbeff07ee7afbd103642cb2baaa508ef293404213e9d9c7f02bcc621

Tx prefix hash: d2385357d77c28e15a99da573d63605c0a7e7740753cd0c45dc53a1e8da3a57c
Tx public key: 9c48dc63dba311e3207e7dd594e9fa810616f4f385d8ca2b3f6326364025402e
Timestamp: 1703993370 Timestamp [UCT]: 2023-12-31 03:29:30 Age [y:d:h:m:s]: 01:318:08:58:18
Block: 924841 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 486386 RingCT/type: yes/0
Extra: 019c48dc63dba311e3207e7dd594e9fa810616f4f385d8ca2b3f6326364025402e021100000002ac328d11000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee7054ffe27f7f67ba3c82f70e53aa929e95e2161ee4b2561b6c69f9a6918c99 0.600000000000 1382601 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": 924851, "vin": [ { "gen": { "height": 924841 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee7054ffe27f7f67ba3c82f70e53aa929e95e2161ee4b2561b6c69f9a6918c99" } } ], "extra": [ 1, 156, 72, 220, 99, 219, 163, 17, 227, 32, 126, 125, 213, 148, 233, 250, 129, 6, 22, 244, 243, 133, 216, 202, 43, 63, 99, 38, 54, 64, 37, 64, 46, 2, 17, 0, 0, 0, 2, 172, 50, 141, 17, 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