Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6534e659171e171d3b292d77f15d6b22d7a54fe59e9fabd87b79d693d00a17a0

Tx prefix hash: 0a2147d48d5d5b8442a0225ddc3137add267e09f7e7e64c410eaee4dc44c500b
Tx public key: 6064f38e52523ff51c693448b6eb8c16744796ce71caadc959c12f60e8fdf190
Timestamp: 1719122510 Timestamp [UCT]: 2024-06-23 06:01:50 Age [y:d:h:m:s]: 01:135:18:40:59
Block: 1050266 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355586 RingCT/type: yes/0
Extra: 016064f38e52523ff51c693448b6eb8c16744796ce71caadc959c12f60e8fdf19002110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35bba9a02ef0a0f03d3632c7749e6132042bc79f386a752266903011e2ce2e1e 0.600000000000 1520427 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": 1050276, "vin": [ { "gen": { "height": 1050266 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35bba9a02ef0a0f03d3632c7749e6132042bc79f386a752266903011e2ce2e1e" } } ], "extra": [ 1, 96, 100, 243, 142, 82, 82, 63, 245, 28, 105, 52, 72, 182, 235, 140, 22, 116, 71, 150, 206, 113, 202, 173, 201, 89, 193, 47, 96, 232, 253, 241, 144, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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