Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11883d133dea2fd74778b954c86fb3b30da7288d6f6621631336f203accda0e9

Tx prefix hash: ba9be20ca2b6b6bb1a49d1d7ddee6da7cc929492df4f26f020ee7940e23cd8b9
Tx public key: 97c6cbf3a207ed4e414e303e9eedf22863e0cf6241ad017af59097916b246115
Timestamp: 1681714190 Timestamp [UCT]: 2023-04-17 06:49:50 Age [y:d:h:m:s]: 01:281:07:01:54
Block: 740385 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 462512 RingCT/type: yes/0
Extra: 0197c6cbf3a207ed4e414e303e9eedf22863e0cf6241ad017af59097916b24611502110000000175e3f0e9000000000000000000

1 output(s) for total of 2.161709663000 dcy

stealth address amount amount idx
00: 9acefdb9951bf37d14bd2b3067410efd6c0224ac8ed6d51e98e99ec591e6b97c 2.161709663000 1187278 of 0

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": 740395, "vin": [ { "gen": { "height": 740385 } } ], "vout": [ { "amount": 2161709663, "target": { "key": "9acefdb9951bf37d14bd2b3067410efd6c0224ac8ed6d51e98e99ec591e6b97c" } } ], "extra": [ 1, 151, 198, 203, 243, 162, 7, 237, 78, 65, 78, 48, 62, 158, 237, 242, 40, 99, 224, 207, 98, 65, 173, 1, 122, 245, 144, 151, 145, 107, 36, 97, 21, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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