Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f805c7b6f78ec8a02a1ae7e9f6130145217667ef72453c9f4ab611ba7bf099c

Tx prefix hash: 1cb87424e0ad3436fb11908fbfbfd002831f42e4f9d75f6f9d8b4e3e3c7c0453
Tx public key: 5ab27ea86cd19616e87d765cc095afd787449acc7fc37e53174aeb995ef43c80
Timestamp: 1668637066 Timestamp [UCT]: 2022-11-16 22:17:46 Age [y:d:h:m:s]: 02:190:20:58:57
Block: 632654 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 658163 RingCT/type: yes/0
Extra: 015ab27ea86cd19616e87d765cc095afd787449acc7fc37e53174aeb995ef43c8002110000000475e3f0e9000000000000000000

1 output(s) for total of 4.917616789000 dcy

stealth address amount amount idx
00: f080e28008230abf39c4b23bf64aadb82b7249b66654a3bd2c29e4d698ff7e37 4.917616789000 1071644 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": 632664, "vin": [ { "gen": { "height": 632654 } } ], "vout": [ { "amount": 4917616789, "target": { "key": "f080e28008230abf39c4b23bf64aadb82b7249b66654a3bd2c29e4d698ff7e37" } } ], "extra": [ 1, 90, 178, 126, 168, 108, 209, 150, 22, 232, 125, 118, 92, 192, 149, 175, 215, 135, 68, 154, 204, 127, 195, 126, 83, 23, 74, 235, 153, 94, 244, 60, 128, 2, 17, 0, 0, 0, 4, 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