Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df697c296a9fc0fb8b8e10e066975b68653203e8db4a2b7e0774793ba68b6e3a

Tx prefix hash: ffaccc0c057b644b25d4c73124cd366143e1db8e624913ef88f40780fab3350e
Tx public key: 1cd390c47797dcac1f81f2efd3ea6dedcf3a7a30db195e89b8149bba302c69dd
Timestamp: 1718157189 Timestamp [UCT]: 2024-06-12 01:53:09 Age [y:d:h:m:s]: 00:215:00:41:53
Block: 1042281 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153877 RingCT/type: yes/0
Extra: 011cd390c47797dcac1f81f2efd3ea6dedcf3a7a30db195e89b8149bba302c69dd021100000002d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d8c92c9bf4ad021f0d3c9bd6cfeae6e81cc1abd58eaa186667c21ac34b41996 0.600000000000 1511160 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": 1042291, "vin": [ { "gen": { "height": 1042281 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d8c92c9bf4ad021f0d3c9bd6cfeae6e81cc1abd58eaa186667c21ac34b41996" } } ], "extra": [ 1, 28, 211, 144, 196, 119, 151, 220, 172, 31, 129, 242, 239, 211, 234, 109, 237, 207, 58, 122, 48, 219, 25, 94, 137, 184, 20, 155, 186, 48, 44, 105, 221, 2, 17, 0, 0, 0, 2, 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