Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f675abeb51cec110d93452744040aa0b8ff58dc34df727878d6cb8c9dcf3fae

Tx prefix hash: 65b51c8b4fbff38404391a4370908417bfecd3e6b010de256aae998837709be5
Tx public key: b2b4f890282fb7d111e827163abb82237a1f24fb9ba2dca80e26aa3cde2ad32d
Timestamp: 1723780262 Timestamp [UCT]: 2024-08-16 03:51:02 Age [y:d:h:m:s]: 00:163:05:48:04
Block: 1088897 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116729 RingCT/type: yes/0
Extra: 01b2b4f890282fb7d111e827163abb82237a1f24fb9ba2dca80e26aa3cde2ad32d021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a72068d8bf2282a3ff4377dd8a27d4459d19b05112546cdf7fe46820cc5d08d 0.600000000000 1563516 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": 1088907, "vin": [ { "gen": { "height": 1088897 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a72068d8bf2282a3ff4377dd8a27d4459d19b05112546cdf7fe46820cc5d08d" } } ], "extra": [ 1, 178, 180, 248, 144, 40, 47, 183, 209, 17, 232, 39, 22, 58, 187, 130, 35, 122, 31, 36, 251, 155, 162, 220, 168, 14, 38, 170, 60, 222, 42, 211, 45, 2, 17, 0, 0, 0, 7, 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