Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eca390e43061ef2a51ef18cfed7dc8bb3b9ec69370a4500e0a7dc1c9758266fe

Tx prefix hash: b1e89dee1693a67ba9afb2b9a5a2e9100ac91841d806735645a66e4beed05a15
Tx public key: 59d0dfbe1f1c2baad72e9a8abee636256fcf20e1eebe5749c7b42ed448387926
Timestamp: 1719094585 Timestamp [UCT]: 2024-06-22 22:16:25 Age [y:d:h:m:s]: 00:327:16:21:25
Block: 1050033 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234200 RingCT/type: yes/0
Extra: 0159d0dfbe1f1c2baad72e9a8abee636256fcf20e1eebe5749c7b42ed448387926021100000004d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f22c4f33d8c22b1008dce19f89aa1cb22299bebe7baeabfbd2a9416ddc9bada 0.600000000000 1520180 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": 1050043, "vin": [ { "gen": { "height": 1050033 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f22c4f33d8c22b1008dce19f89aa1cb22299bebe7baeabfbd2a9416ddc9bada" } } ], "extra": [ 1, 89, 208, 223, 190, 31, 28, 43, 170, 215, 46, 154, 138, 190, 230, 54, 37, 111, 207, 32, 225, 238, 190, 87, 73, 199, 180, 46, 212, 72, 56, 121, 38, 2, 17, 0, 0, 0, 4, 215, 73, 245, 17, 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