Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b8b3b707ce2ddee579050bd0e6d18db40e7da5846cb51684795f311c82e8452

Tx prefix hash: bb76e2bbc001dee9c3374fb14462eba51ec13fff15bc28dc5bb907f67ed53e22
Tx public key: 76d4e12d498dd2d582b021be6f2fb1c38eea36613c1c018d9558d6af4995185d
Timestamp: 1714347059 Timestamp [UCT]: 2024-04-28 23:30:59 Age [y:d:h:m:s]: 00:260:10:40:16
Block: 1010682 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186422 RingCT/type: yes/0
Extra: 0176d4e12d498dd2d582b021be6f2fb1c38eea36613c1c018d9558d6af4995185d0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d11d861e81d190b50ee7af2ad968390b4dc962b0fd178a16791ef64d6f2d80b9 0.600000000000 1472708 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": 1010692, "vin": [ { "gen": { "height": 1010682 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d11d861e81d190b50ee7af2ad968390b4dc962b0fd178a16791ef64d6f2d80b9" } } ], "extra": [ 1, 118, 212, 225, 45, 73, 141, 210, 213, 130, 176, 33, 190, 111, 47, 177, 195, 142, 234, 54, 97, 60, 28, 1, 141, 149, 88, 214, 175, 73, 149, 24, 93, 2, 17, 0, 0, 0, 3, 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