Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f1b30b50c6f872ad231e6d12326f4be1968dab1de0c0c0a917793044c514b8d

Tx prefix hash: 3cc25cf4d86c863c424da6e3de9745418967915a794404a668afd1682c0d58b8
Tx public key: f96d76902e736e2cdfc3ac54fdb357426555c99dbce34be0afc84cc8c45a014e
Timestamp: 1700257877 Timestamp [UCT]: 2023-11-17 21:51:17 Age [y:d:h:m:s]: 01:129:01:09:07
Block: 893881 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353395 RingCT/type: yes/0
Extra: 01f96d76902e736e2cdfc3ac54fdb357426555c99dbce34be0afc84cc8c45a014e021100000003faf35c9c000000000000000000

1 output(s) for total of 0.670194982000 dcy

stealth address amount amount idx
00: ec367d24028359a517f27e227bf52183a4f7dfd4fcf9c5f4e17c3594e4717107 0.670194982000 1350066 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": 893891, "vin": [ { "gen": { "height": 893881 } } ], "vout": [ { "amount": 670194982, "target": { "key": "ec367d24028359a517f27e227bf52183a4f7dfd4fcf9c5f4e17c3594e4717107" } } ], "extra": [ 1, 249, 109, 118, 144, 46, 115, 110, 44, 223, 195, 172, 84, 253, 179, 87, 66, 101, 85, 201, 157, 188, 227, 75, 224, 175, 200, 76, 200, 196, 90, 1, 78, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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