Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84edac5859dea90d0c65ff0e9e735b1f4da756cbef98b2dd7f0ec1ceae1de2f6

Tx prefix hash: cc59cdebb194db03a02792288f9a976a06c5c7641934aaeac74f90e5485f080b
Tx public key: 4d3e0caa8aea7a420d728ef82ecbb2648d75756ffa2e12f78b63acd9d203ade4
Timestamp: 1727914736 Timestamp [UCT]: 2024-10-03 00:18:56 Age [y:d:h:m:s]: 00:178:05:40:39
Block: 1123178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127171 RingCT/type: yes/0
Extra: 014d3e0caa8aea7a420d728ef82ecbb2648d75756ffa2e12f78b63acd9d203ade4021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: efa18a49bd37353b8a3e75f61dfe26175f5dd2861674f39dd233224124ea06b7 0.600000000000 1605711 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": 1123188, "vin": [ { "gen": { "height": 1123178 } } ], "vout": [ { "amount": 600000000, "target": { "key": "efa18a49bd37353b8a3e75f61dfe26175f5dd2861674f39dd233224124ea06b7" } } ], "extra": [ 1, 77, 62, 12, 170, 138, 234, 122, 66, 13, 114, 142, 248, 46, 203, 178, 100, 141, 117, 117, 111, 250, 46, 18, 247, 139, 99, 172, 217, 210, 3, 173, 228, 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