Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a7bf6bcb85afac731829dd2e1026f9ac315543b01146c9300355834cdc46ce2

Tx prefix hash: 6b4acdd39381b90245922696d8cf8f52e2ca4ea1cf7716492f5a328d92d331ee
Tx public key: 4988639f93418627d37c0d9f67a82070eac64e44ce27cb7a9ff4fc58c0e94d57
Timestamp: 1722606038 Timestamp [UCT]: 2024-08-02 13:40:38 Age [y:d:h:m:s]: 00:247:14:51:31
Block: 1079164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176856 RingCT/type: yes/0
Extra: 014988639f93418627d37c0d9f67a82070eac64e44ce27cb7a9ff4fc58c0e94d57021100000001ef5a8513000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 09fd89c3066fa917ff5c2c33a13363f8c5601f6fbf2a1d6787e1f9342c3f621a 0.600000000000 1551997 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": 1079174, "vin": [ { "gen": { "height": 1079164 } } ], "vout": [ { "amount": 600000000, "target": { "key": "09fd89c3066fa917ff5c2c33a13363f8c5601f6fbf2a1d6787e1f9342c3f621a" } } ], "extra": [ 1, 73, 136, 99, 159, 147, 65, 134, 39, 211, 124, 13, 159, 103, 168, 32, 112, 234, 198, 78, 68, 206, 39, 203, 122, 159, 244, 252, 88, 192, 233, 77, 87, 2, 17, 0, 0, 0, 1, 239, 90, 133, 19, 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