Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b82b63173897f9eba4442e79e1aa304e7b5fcc442b8c3c4e9fa236ed28fe9299

Tx prefix hash: aab7bb68f14e273366aedc6c0005d4e7ca93629497cf80dd1d88ef4835d597b8
Tx public key: 815f7736a8e3a561f101011a2e56e808f0f9b1ceb448ddfc46dc28f024947a32
Timestamp: 1726942350 Timestamp [UCT]: 2024-09-21 18:12:30 Age [y:d:h:m:s]: 00:112:01:37:49
Block: 1115110 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80120 RingCT/type: yes/0
Extra: 01815f7736a8e3a561f101011a2e56e808f0f9b1ceb448ddfc46dc28f024947a3202110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39ef5421ef17baef62f99c45f3930c6cc00c75eb7f677a417a27dd5fe707f28e 0.600000000000 1595129 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": 1115120, "vin": [ { "gen": { "height": 1115110 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39ef5421ef17baef62f99c45f3930c6cc00c75eb7f677a417a27dd5fe707f28e" } } ], "extra": [ 1, 129, 95, 119, 54, 168, 227, 165, 97, 241, 1, 1, 26, 46, 86, 232, 8, 240, 249, 177, 206, 180, 72, 221, 252, 70, 220, 40, 240, 36, 148, 122, 50, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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