Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 988035cfac9f35203514090cef50465fbd7a11d0c5ef02c1b37a1f9ebfff0094

Tx prefix hash: d1c85e9de83694b3da199b6aa44fef20f479665c8a2ddd12b2796ba957c69131
Tx public key: 06d8beec8eaef8d1c47c88ba385751cfd02c48c49310105d5ea5ab3e066785f3
Timestamp: 1722663877 Timestamp [UCT]: 2024-08-03 05:44:37 Age [y:d:h:m:s]: 00:161:00:46:29
Block: 1079646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115209 RingCT/type: yes/0
Extra: 0106d8beec8eaef8d1c47c88ba385751cfd02c48c49310105d5ea5ab3e066785f302110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2199cf68f71f6fd63a4e574ed603e5538a825e86764c4964cea1139c5b47126c 0.600000000000 1552691 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": 1079656, "vin": [ { "gen": { "height": 1079646 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2199cf68f71f6fd63a4e574ed603e5538a825e86764c4964cea1139c5b47126c" } } ], "extra": [ 1, 6, 216, 190, 236, 142, 174, 248, 209, 196, 124, 136, 186, 56, 87, 81, 207, 208, 44, 72, 196, 147, 16, 16, 93, 94, 165, 171, 62, 6, 103, 133, 243, 2, 17, 0, 0, 0, 9, 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