Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25c4d24f7c029c7963445222b9be011fc19a4b33f264d887b8574951f6b8901b

Tx prefix hash: ddc0396567638536dedfd467f02c3f259ce9dc6f9a2d78eca4455a844cd67f68
Tx public key: 9dcb0e2c1a6b64487fe8ea890c6e593c116b2db628006aca351771831a77c631
Timestamp: 1716973826 Timestamp [UCT]: 2024-05-29 09:10:26 Age [y:d:h:m:s]: 01:163:08:35:33
Block: 1032476 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375329 RingCT/type: yes/0
Extra: 019dcb0e2c1a6b64487fe8ea890c6e593c116b2db628006aca351771831a77c63102110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5b218fb42a2156dbc54581f39fba922373f985bc7fd48e9a30f20080467e0cb 0.600000000000 1500929 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": 1032486, "vin": [ { "gen": { "height": 1032476 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5b218fb42a2156dbc54581f39fba922373f985bc7fd48e9a30f20080467e0cb" } } ], "extra": [ 1, 157, 203, 14, 44, 26, 107, 100, 72, 127, 232, 234, 137, 12, 110, 89, 60, 17, 107, 45, 182, 40, 0, 106, 202, 53, 23, 113, 131, 26, 119, 198, 49, 2, 17, 0, 0, 0, 2, 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