Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2762fecaa48759c7606bc28cb3bad39447493fb83233eedc93d07af0e837900e

Tx prefix hash: cddcddd619eeb8288d79d0559e23aa1e5aecaf737d667d600d362eb1e35d8f2a
Tx public key: 2a365e86e26e5ea389994941cd8df4540671a41de6c55fa017dd0aaadd61b4b2
Timestamp: 1687018853 Timestamp [UCT]: 2023-06-17 16:20:53 Age [y:d:h:m:s]: 01:203:13:04:50
Block: 784383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 406869 RingCT/type: yes/0
Extra: 012a365e86e26e5ea389994941cd8df4540671a41de6c55fa017dd0aaadd61b4b2021100000003e6d27f9c000000000000000000

1 output(s) for total of 1.545303047000 dcy

stealth address amount amount idx
00: 41b140df2d03484305e4d0fab55dafb8512a5aa094fd3b68bfe3f91b8a686cee 1.545303047000 1234270 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": 784393, "vin": [ { "gen": { "height": 784383 } } ], "vout": [ { "amount": 1545303047, "target": { "key": "41b140df2d03484305e4d0fab55dafb8512a5aa094fd3b68bfe3f91b8a686cee" } } ], "extra": [ 1, 42, 54, 94, 134, 226, 110, 94, 163, 137, 153, 73, 65, 205, 141, 244, 84, 6, 113, 164, 29, 230, 197, 95, 160, 23, 221, 10, 170, 221, 97, 180, 178, 2, 17, 0, 0, 0, 3, 230, 210, 127, 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