Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ecac079d0265bf4d0c7893ce18318516e924e7aa6aa41c83903d95e4806b0e1d

Tx prefix hash: b598a85e7a8135c15d0bf8683cc9863aa93751beba987017cb22d494d16aa9f5
Tx public key: 65a8e5e4bece346d46f1c99443f722363f0e801f1b046e36181c9a2d14caa2bb
Timestamp: 1728363139 Timestamp [UCT]: 2024-10-08 04:52:19 Age [y:d:h:m:s]: 00:209:14:53:43
Block: 1126886 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149623 RingCT/type: yes/0
Extra: 0165a8e5e4bece346d46f1c99443f722363f0e801f1b046e36181c9a2d14caa2bb021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: abebfb30f63c8838cd4e849742bcf243f4c70a0ac011922c9215a0c67402d3f6 0.600000000000 1609683 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": 1126896, "vin": [ { "gen": { "height": 1126886 } } ], "vout": [ { "amount": 600000000, "target": { "key": "abebfb30f63c8838cd4e849742bcf243f4c70a0ac011922c9215a0c67402d3f6" } } ], "extra": [ 1, 101, 168, 229, 228, 190, 206, 52, 109, 70, 241, 201, 148, 67, 247, 34, 54, 63, 14, 128, 31, 27, 4, 110, 54, 24, 28, 154, 45, 20, 202, 162, 187, 2, 17, 0, 0, 0, 1, 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