Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2de2ca35576df7b3de55a5b1258570c7013d0c12e701dd3cf51b5046a06d1cd4

Tx prefix hash: c7a203be385f21c6e57a66fa0c613a5e094a1f9f27d93971942b62d6d6cbad09
Tx public key: bece37ae48f927a7fa89f3824b96184356c5695889c982cce2cbfcd346e1b4e8
Timestamp: 1720845986 Timestamp [UCT]: 2024-07-13 04:46:26 Age [y:d:h:m:s]: 00:275:11:09:45
Block: 1064583 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196792 RingCT/type: yes/0
Extra: 01bece37ae48f927a7fa89f3824b96184356c5695889c982cce2cbfcd346e1b4e8021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b39e137171754e3ac6652d91c157715b14cfd9191ca484abf6cf3c3d656ea505 0.600000000000 1535112 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": 1064593, "vin": [ { "gen": { "height": 1064583 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b39e137171754e3ac6652d91c157715b14cfd9191ca484abf6cf3c3d656ea505" } } ], "extra": [ 1, 190, 206, 55, 174, 72, 249, 39, 167, 250, 137, 243, 130, 75, 150, 24, 67, 86, 197, 105, 88, 137, 201, 130, 204, 226, 203, 252, 211, 70, 225, 180, 232, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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