Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c2081feebb5ba76f06c22b823aee45fbc2c4fc3316967659743c250384c8662

Tx prefix hash: 0e1380e9e937f84a08f88e789364b5a7d6c50ca7ba8b0422377d362b4a05cbff
Tx public key: 900efe4f8d6f3d5bdf0a06e22668661e944a01743e5806a2879373eb5a5e3d03
Timestamp: 1708205205 Timestamp [UCT]: 2024-02-17 21:26:45 Age [y:d:h:m:s]: 01:262:04:24:08
Block: 959764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 446117 RingCT/type: yes/0
Extra: 01900efe4f8d6f3d5bdf0a06e22668661e944a01743e5806a2879373eb5a5e3d030211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac9bf349d218ffb78eec21f50a96f2e9de5ebdd684afa991ce8f68a466906468 0.600000000000 1419317 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": 959774, "vin": [ { "gen": { "height": 959764 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac9bf349d218ffb78eec21f50a96f2e9de5ebdd684afa991ce8f68a466906468" } } ], "extra": [ 1, 144, 14, 254, 79, 141, 111, 61, 91, 223, 10, 6, 226, 38, 104, 102, 30, 148, 74, 1, 116, 62, 88, 6, 162, 135, 147, 115, 235, 90, 94, 61, 3, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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