Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d2b3e9db6aecdac931fbb989e6590eb8b8119ca086653aeccaee40647495ce6

Tx prefix hash: dddb40f1ff80471cf8ab325bbfa8da5e44eeb012e5ae88537ea6b370e67210df
Tx public key: 0dc3c73b61f05bb32e4602907984fcce8cf827e0254f820803a3db3fabcaa8d9
Timestamp: 1704379394 Timestamp [UCT]: 2024-01-04 14:43:14 Age [y:d:h:m:s]: 01:125:23:38:38
Block: 928054 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351157 RingCT/type: yes/0
Extra: 010dc3c73b61f05bb32e4602907984fcce8cf827e0254f820803a3db3fabcaa8d9021100000009e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ebf8f577ec20148b8729b3c0c82dc79b353a94e546b1c89bb282b238d94cc81 0.600000000000 1385910 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": 928064, "vin": [ { "gen": { "height": 928054 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ebf8f577ec20148b8729b3c0c82dc79b353a94e546b1c89bb282b238d94cc81" } } ], "extra": [ 1, 13, 195, 199, 59, 97, 240, 91, 179, 46, 70, 2, 144, 121, 132, 252, 206, 140, 248, 39, 224, 37, 79, 130, 8, 3, 163, 219, 63, 171, 202, 168, 217, 2, 17, 0, 0, 0, 9, 224, 133, 50, 182, 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