Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbc40e5e8888c8436f22502d3d225d1f7f6020b3211bac2a0a121c4aeb793a01

Tx prefix hash: c6fd493b60862ae33a4da73abd693e52f547d5e49d2dd3c8f5f81fa7d64f47be
Tx public key: 23bb0cd621a708ac17eb41d48a745f5181fd7010987ecea927d86ae94ad5642d
Timestamp: 1696733314 Timestamp [UCT]: 2023-10-08 02:48:34 Age [y:d:h:m:s]: 01:085:23:05:09
Block: 864870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322679 RingCT/type: yes/0
Extra: 0123bb0cd621a708ac17eb41d48a745f5181fd7010987ecea927d86ae94ad5642d02110000000233af99f4000000000000000000

1 output(s) for total of 0.836231841000 dcy

stealth address amount amount idx
00: c178d4211d1ff0e6e169f5414a16d9d94a1ee8b71e3c83450a9c684433059113 0.836231841000 1319392 of 0

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": 864880, "vin": [ { "gen": { "height": 864870 } } ], "vout": [ { "amount": 836231841, "target": { "key": "c178d4211d1ff0e6e169f5414a16d9d94a1ee8b71e3c83450a9c684433059113" } } ], "extra": [ 1, 35, 187, 12, 214, 33, 167, 8, 172, 23, 235, 65, 212, 138, 116, 95, 81, 129, 253, 112, 16, 152, 126, 206, 169, 39, 216, 106, 233, 74, 213, 100, 45, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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