Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df18555bdc4e63f5ac63cf75746a59ab17bf3dda35862fd5aaf61324917ef320

Tx prefix hash: 420325a3111b331e9d4125cb60bd277d9329135ceb70854fdc5fbf3b7ca11623
Tx public key: 3799cb6dae10a4c61fea6f4949aec1dad75d623454dee4b1987a9a4a48e55da9
Timestamp: 1737180717 Timestamp [UCT]: 2025-01-18 06:11:57 Age [y:d:h:m:s]: 00:058:06:18:27
Block: 1199845 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41424 RingCT/type: yes/0
Extra: 013799cb6dae10a4c61fea6f4949aec1dad75d623454dee4b1987a9a4a48e55da90211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d9ca939a59d543804ccb1a1735a8d4451d2148ff9b92f9dfbcf17dd3570cf0a 0.600000000000 1686478 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": 1199855, "vin": [ { "gen": { "height": 1199845 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d9ca939a59d543804ccb1a1735a8d4451d2148ff9b92f9dfbcf17dd3570cf0a" } } ], "extra": [ 1, 55, 153, 203, 109, 174, 16, 164, 198, 31, 234, 111, 73, 73, 174, 193, 218, 215, 93, 98, 52, 84, 222, 228, 177, 152, 122, 154, 74, 72, 229, 93, 169, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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