Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4de68e009433d4b0a8e3e9359e39c2cd95a91ef3b955be92118f663f1a0c8b64

Tx prefix hash: 4524a5de666c96a248302e1a812b0b1ea281de6a87734a4d52c1d6039525c5a1
Tx public key: 8aaa4d83e7badea3903c0345a4c7d15e28dc929efead4401c446488dc0544871
Timestamp: 1737312311 Timestamp [UCT]: 2025-01-19 18:45:11 Age [y:d:h:m:s]: 00:331:19:46:41
Block: 1200902 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234729 RingCT/type: yes/0
Extra: 018aaa4d83e7badea3903c0345a4c7d15e28dc929efead4401c446488dc0544871021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b723f5f58ca6bc1f14aaef4799a32bee08c053d7fd3de2fa1b0eea87d0cba2e 0.600000000000 1687549 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": 1200912, "vin": [ { "gen": { "height": 1200902 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b723f5f58ca6bc1f14aaef4799a32bee08c053d7fd3de2fa1b0eea87d0cba2e" } } ], "extra": [ 1, 138, 170, 77, 131, 231, 186, 222, 163, 144, 60, 3, 69, 164, 199, 209, 94, 40, 220, 146, 158, 254, 173, 68, 1, 196, 70, 72, 141, 192, 84, 72, 113, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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