Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38e62697ce7847314a5bc0159f808d537f437ca421342376f184d8f7bb406e7f

Tx prefix hash: ba4731875fbca482a2d82ee94c6ae326e26662d5b17c63389852540e75812c4c
Tx public key: 1ebaa3b4733133e89df7b0e69789e8d0cc330d16bd0cb54113ed745708b943b3
Timestamp: 1648862296 Timestamp [UCT]: 2022-04-02 01:18:16 Age [y:d:h:m:s]: 03:217:04:22:19
Block: 471298 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 933282 RingCT/type: yes/0
Extra: 011ebaa3b4733133e89df7b0e69789e8d0cc330d16bd0cb54113ed745708b943b3021100000002c9067537000000000000000000

1 output(s) for total of 16.842025806000 dcy

stealth address amount amount idx
00: 75ba603d2a0715f83a2b580193c71fdc2ad9d211cc82ef5bfb7eaa36a3684d49 16.842025806000 890608 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": 471308, "vin": [ { "gen": { "height": 471298 } } ], "vout": [ { "amount": 16842025806, "target": { "key": "75ba603d2a0715f83a2b580193c71fdc2ad9d211cc82ef5bfb7eaa36a3684d49" } } ], "extra": [ 1, 30, 186, 163, 180, 115, 49, 51, 232, 157, 247, 176, 230, 151, 137, 232, 208, 204, 51, 13, 22, 189, 12, 181, 65, 19, 237, 116, 87, 8, 185, 67, 179, 2, 17, 0, 0, 0, 2, 201, 6, 117, 55, 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