Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4357ce97bb56e215805afbf475e320a8b84fa06cc4e8eb63195887b0c70afed1

Tx prefix hash: 81a4d3f5e23c1fe427aae7fa0e806bd2b0c312c6a2dca48ec92ac09789842d3d
Tx public key: 741aaeb4103b79a1cf1b3ca072721bfe88e193832d66744e0bc6bcabc80591ce
Timestamp: 1727397852 Timestamp [UCT]: 2024-09-27 00:44:12 Age [y:d:h:m:s]: 00:171:04:14:16
Block: 1118886 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122156 RingCT/type: yes/0
Extra: 01741aaeb4103b79a1cf1b3ca072721bfe88e193832d66744e0bc6bcabc80591ce021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b1cec994ce365a80d358f5e6f157306aa0ef7f545b1e09b6ae3f5c945a53135 0.600000000000 1600235 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": 1118896, "vin": [ { "gen": { "height": 1118886 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b1cec994ce365a80d358f5e6f157306aa0ef7f545b1e09b6ae3f5c945a53135" } } ], "extra": [ 1, 116, 26, 174, 180, 16, 59, 121, 161, 207, 27, 60, 160, 114, 114, 27, 254, 136, 225, 147, 131, 45, 102, 116, 78, 11, 198, 188, 171, 200, 5, 145, 206, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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