Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7a09e875a1421945793ca60b28e949634508eafef05e2de2c917773ae43b896

Tx prefix hash: 8db8ee51d8ad8178f7fd4ac7bd78be8b34c363c253973bd9899c149c7e850fde
Tx public key: d3555e18b4b7b25037e7c8d8e690d0ac7ca14e5d079ccbe7824a4e8954426fe6
Timestamp: 1702540433 Timestamp [UCT]: 2023-12-14 07:53:53 Age [y:d:h:m:s]: 01:118:07:04:46
Block: 912804 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345687 RingCT/type: yes/0
Extra: 01d3555e18b4b7b25037e7c8d8e690d0ac7ca14e5d079ccbe7824a4e8954426fe6021100000001faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27785b73c9f5609e3d8bfe10fc651134cd81cb12c0ab345c6d4e55df725165ab 0.600000000000 1370040 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": 912814, "vin": [ { "gen": { "height": 912804 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27785b73c9f5609e3d8bfe10fc651134cd81cb12c0ab345c6d4e55df725165ab" } } ], "extra": [ 1, 211, 85, 94, 24, 180, 183, 178, 80, 55, 231, 200, 216, 230, 144, 208, 172, 124, 161, 78, 93, 7, 156, 203, 231, 130, 74, 78, 137, 84, 66, 111, 230, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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