Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 877395639ab5543b9f7c45b75b5ea9f6f29f22f327e9640ab3b382e04d74f7e5

Tx prefix hash: fd8f2375f9f11058fce3d76a4f3561a53044719fe1988ec5ba1e41b25afb36af
Tx public key: 979e9b8675ed708b1033d47081fb4a69cb334574c5d847f0665485290074f49c
Timestamp: 1727903997 Timestamp [UCT]: 2024-10-02 21:19:57 Age [y:d:h:m:s]: 01:061:05:26:25
Block: 1123084 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302177 RingCT/type: yes/0
Extra: 01979e9b8675ed708b1033d47081fb4a69cb334574c5d847f0665485290074f49c02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3514d81af9bf0e90f3f580cdb8dc6387000fdc78529e8f690aa42356de9a3c9c 0.600000000000 1605617 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": 1123094, "vin": [ { "gen": { "height": 1123084 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3514d81af9bf0e90f3f580cdb8dc6387000fdc78529e8f690aa42356de9a3c9c" } } ], "extra": [ 1, 151, 158, 155, 134, 117, 237, 112, 139, 16, 51, 212, 112, 129, 251, 74, 105, 203, 51, 69, 116, 197, 216, 71, 240, 102, 84, 133, 41, 0, 116, 244, 156, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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