Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1ff841b9374b44ae5b3220a4b06d30e5a44872f45c402761fd86148575fefb3

Tx prefix hash: 8246e98adea0a60b7fcf26d241fce28bfa223610712fd870436ec6f18ce706ef
Tx public key: 9866aae98383e166e85001783d06b3dd83874e2a1650c9f777cf6feb6d8eaf76
Timestamp: 1711018480 Timestamp [UCT]: 2024-03-21 10:54:40 Age [y:d:h:m:s]: 01:016:05:27:13
Block: 983118 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272543 RingCT/type: yes/0
Extra: 019866aae98383e166e85001783d06b3dd83874e2a1650c9f777cf6feb6d8eaf7602110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f2de20ef32d0de1fdfbe499c6b1d51a28478d060703d215a74c95b16e3a413d 0.600000000000 1443241 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": 983128, "vin": [ { "gen": { "height": 983118 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f2de20ef32d0de1fdfbe499c6b1d51a28478d060703d215a74c95b16e3a413d" } } ], "extra": [ 1, 152, 102, 170, 233, 131, 131, 225, 102, 232, 80, 1, 120, 61, 6, 179, 221, 131, 135, 78, 42, 22, 80, 201, 247, 119, 207, 111, 235, 109, 142, 175, 118, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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