Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be4c8142436260b63cf568b6e0a4d062ec54169571d1c3f66552977a244ed520

Tx prefix hash: ab05c79c492748e0e904d5eb9d2fb6819c4f934e54bb5f3db07a1def5047998c
Tx public key: b28d0a8cea618e45c18af3adbd3dad655aa72d01801be88c4bac0744a48a5b61
Timestamp: 1646143573 Timestamp [UCT]: 2022-03-01 14:06:13 Age [y:d:h:m:s]: 03:049:03:49:38
Block: 449103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 815202 RingCT/type: yes/0
Extra: 01b28d0a8cea618e45c18af3adbd3dad655aa72d01801be88c4bac0744a48a5b6102110000000dd3fcec30000000000000000000

1 output(s) for total of 19.951645104000 dcy

stealth address amount amount idx
00: 741c71d95bb2742987e747ab9c5d5d1f46a1f501f37bc5c60686d680861b39fd 19.951645104000 863624 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": 449113, "vin": [ { "gen": { "height": 449103 } } ], "vout": [ { "amount": 19951645104, "target": { "key": "741c71d95bb2742987e747ab9c5d5d1f46a1f501f37bc5c60686d680861b39fd" } } ], "extra": [ 1, 178, 141, 10, 140, 234, 97, 142, 69, 193, 138, 243, 173, 189, 61, 173, 101, 90, 167, 45, 1, 128, 27, 232, 140, 75, 172, 7, 68, 164, 138, 91, 97, 2, 17, 0, 0, 0, 13, 211, 252, 236, 48, 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