Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95d0ffb14dcbdd23ac03a57e848a6bcb247c12554453ac7321536232b86d6072

Tx prefix hash: 0f78441b63c5292f789635b99dad9a82ee1b38e5327d0a71b7bc81d23411d79c
Tx public key: 2c1303ae6dc34ed3ea62341487177a3ad4a43e8e8b1a877a2c680832be2526eb
Timestamp: 1712651197 Timestamp [UCT]: 2024-04-09 08:26:37 Age [y:d:h:m:s]: 01:210:17:24:16
Block: 996608 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 409273 RingCT/type: yes/0
Extra: 012c1303ae6dc34ed3ea62341487177a3ad4a43e8e8b1a877a2c680832be2526eb0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63fd392f24bade432337a7b1a08d55481aef8827dd4e00db9dc3b64ca6649adb 0.600000000000 1457030 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": 996618, "vin": [ { "gen": { "height": 996608 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63fd392f24bade432337a7b1a08d55481aef8827dd4e00db9dc3b64ca6649adb" } } ], "extra": [ 1, 44, 19, 3, 174, 109, 195, 78, 211, 234, 98, 52, 20, 135, 23, 122, 58, 212, 164, 62, 142, 139, 26, 135, 122, 44, 104, 8, 50, 190, 37, 38, 235, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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