Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a19b98b57e34fcc90d23bfa9eab4579b153e5d16e73041ecf679a87aa182a473

Tx prefix hash: cf34fd9e5ad157dc9c470a3c24545703b64582146a9608d6602d69d85a70ae4a
Tx public key: 3e908574890198e48fca3b1e3656a2199d6fdde319ce5fd65d99a5a65577013e
Timestamp: 1710754251 Timestamp [UCT]: 2024-03-18 09:30:51 Age [y:d:h:m:s]: 01:027:12:36:59
Block: 980924 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280633 RingCT/type: yes/0
Extra: 013e908574890198e48fca3b1e3656a2199d6fdde319ce5fd65d99a5a65577013e02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f94206f37307f35686b4c347f805cc5c533cf73df52aac26be14cc0428f39ff7 0.600000000000 1441009 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": 980934, "vin": [ { "gen": { "height": 980924 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f94206f37307f35686b4c347f805cc5c533cf73df52aac26be14cc0428f39ff7" } } ], "extra": [ 1, 62, 144, 133, 116, 137, 1, 152, 228, 143, 202, 59, 30, 54, 86, 162, 25, 157, 111, 221, 227, 25, 206, 95, 214, 93, 153, 165, 166, 85, 119, 1, 62, 2, 17, 0, 0, 0, 3, 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