Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da6abdca2dd3912fd4a29f40afee1a1810d58f3e92e7e8949e9cba566aeab6a3

Tx prefix hash: 1cc913c50f3ff14ab825a091eca5a25ddb25499b4331678d9dfc2e004e7ac682
Tx public key: 1e09a1fc922980c4165d43f54d3e83c7d35c8b0a79bb5398901460c99ab73c08
Timestamp: 1705589468 Timestamp [UCT]: 2024-01-18 14:51:08 Age [y:d:h:m:s]: 01:351:22:35:55
Block: 938064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 510443 RingCT/type: yes/0
Extra: 011e09a1fc922980c4165d43f54d3e83c7d35c8b0a79bb5398901460c99ab73c0802110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14cfb010923a339a734d9ae043142af041c733458c1e18fe33385dc9def370ce 0.600000000000 1396128 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": 938074, "vin": [ { "gen": { "height": 938064 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14cfb010923a339a734d9ae043142af041c733458c1e18fe33385dc9def370ce" } } ], "extra": [ 1, 30, 9, 161, 252, 146, 41, 128, 196, 22, 93, 67, 245, 77, 62, 131, 199, 211, 92, 139, 10, 121, 187, 83, 152, 144, 20, 96, 201, 154, 183, 60, 8, 2, 17, 0, 0, 0, 9, 89, 218, 211, 245, 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