Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4315cf3b4be2798ab9a28bea8b76ee61717651d0c02bb5520a4df95a64f75006

Tx prefix hash: eb59b03834ee8ed47bde75089a5748c59f5ecccacdf23e9d3913fcca502229b0
Tx public key: d1a66a53aa2a5a5d2b8bae55e3f2e0c661581b5b8674e83673dba4091a1179ba
Timestamp: 1708331771 Timestamp [UCT]: 2024-02-19 08:36:11 Age [y:d:h:m:s]: 01:093:10:27:04
Block: 960819 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327853 RingCT/type: yes/0
Extra: 01d1a66a53aa2a5a5d2b8bae55e3f2e0c661581b5b8674e83673dba4091a1179ba02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3d33732486724735293d6877c4746c288a7743e43c49262dfa78f8fd49383db 0.600000000000 1420406 of 15

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": 960829, "vin": [ { "gen": { "height": 960819 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3d33732486724735293d6877c4746c288a7743e43c49262dfa78f8fd49383db" } } ], "extra": [ 1, 209, 166, 106, 83, 170, 42, 90, 93, 43, 139, 174, 85, 227, 242, 224, 198, 97, 88, 27, 91, 134, 116, 232, 54, 115, 219, 164, 9, 26, 17, 121, 186, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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