Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5676cbabefe8f2f519d1d77f0455280551c3ab5cc4d1214bcde5a192da50f2a8

Tx prefix hash: 5ab7454407aea8a2707eb4dc60326816a12486784c79f4321468547c4d78af74
Tx public key: 2928b5765f183fce241288c61aa374d0379b06e43daa16abf51c304eea9f63f5
Timestamp: 1724388539 Timestamp [UCT]: 2024-08-23 04:48:59 Age [y:d:h:m:s]: 00:232:18:03:47
Block: 1093952 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166196 RingCT/type: yes/0
Extra: 012928b5765f183fce241288c61aa374d0379b06e43daa16abf51c304eea9f63f5021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df2e607c23cb652f101e50f89f80b5cdfa5b9ae7298794d5d19f4290bfc8d67a 0.600000000000 1568999 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": 1093962, "vin": [ { "gen": { "height": 1093952 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df2e607c23cb652f101e50f89f80b5cdfa5b9ae7298794d5d19f4290bfc8d67a" } } ], "extra": [ 1, 41, 40, 181, 118, 95, 24, 63, 206, 36, 18, 136, 198, 26, 163, 116, 208, 55, 155, 6, 228, 61, 170, 22, 171, 245, 28, 48, 78, 234, 159, 99, 245, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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