Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b8fafc6d8d1137c9e034445ac2b65a815944054a516b20f905de2e4eb0a8016

Tx prefix hash: cb2846e88f2b6d51762e0852e646a34830899549528097edc95c0debc7fb1f65
Tx public key: 888b5116ea960ef30ad1f0131303561a444dbce3cce7194fd6f5a890f901645e
Timestamp: 1629314558 Timestamp [UCT]: 2021-08-18 19:22:38 Age [y:d:h:m:s]: 04:076:01:50:38
Block: 316622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1086278 RingCT/type: yes/0
Extra: 01888b5116ea960ef30ad1f0131303561a444dbce3cce7194fd6f5a890f901645e021100000013e6f80b5a000000000000000000

1 output(s) for total of 54.815116832000 dcy

stealth address amount amount idx
00: d0e2fc47c069fd5d483fe2ee2229ac2cbf6d8475055a487b40ea78f027de1d8d 54.815116832000 658637 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": 316632, "vin": [ { "gen": { "height": 316622 } } ], "vout": [ { "amount": 54815116832, "target": { "key": "d0e2fc47c069fd5d483fe2ee2229ac2cbf6d8475055a487b40ea78f027de1d8d" } } ], "extra": [ 1, 136, 139, 81, 22, 234, 150, 14, 243, 10, 209, 240, 19, 19, 3, 86, 26, 68, 77, 188, 227, 204, 231, 25, 79, 214, 245, 168, 144, 249, 1, 100, 94, 2, 17, 0, 0, 0, 19, 230, 248, 11, 90, 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