Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: efffa21148dab848c33de63f04099734eab42a50feb6194a5e5b2247f370883b

Tx prefix hash: b4fb9dfb2a69e2b9f9da01735d2125da259f7cfc9f4139df63bd51f8456c8d7e
Tx public key: 9d6099c46358e153e510ca4713b4495a75fadd1ad449c4db7ff37d935de14ba6
Timestamp: 1726454921 Timestamp [UCT]: 2024-09-16 02:48:41 Age [y:d:h:m:s]: 00:116:21:21:20
Block: 1111069 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83584 RingCT/type: yes/0
Extra: 019d6099c46358e153e510ca4713b4495a75fadd1ad449c4db7ff37d935de14ba6021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e549e00c1dfeddf56ceeac4c3f5ba1dce3153a2d4eef6f1afaf97e344287af4d 0.600000000000 1589898 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": 1111079, "vin": [ { "gen": { "height": 1111069 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e549e00c1dfeddf56ceeac4c3f5ba1dce3153a2d4eef6f1afaf97e344287af4d" } } ], "extra": [ 1, 157, 96, 153, 196, 99, 88, 225, 83, 229, 16, 202, 71, 19, 180, 73, 90, 117, 250, 221, 26, 212, 73, 196, 219, 127, 243, 125, 147, 93, 225, 75, 166, 2, 17, 0, 0, 0, 3, 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