Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e14fa3a74b42b1608c0d2e6c637f394509faabd0d594c38dab3f4f84d52511d

Tx prefix hash: c868c28e579bc0ddee6855a7818867e9840e47df5f8c5a8ec54a9c05f943e6f4
Tx public key: 64f220eedba3791a38e7ad1eea8af48d656a0b609859c6a8473919a0db4fa0e0
Timestamp: 1763417622 Timestamp [UCT]: 2025-11-17 22:13:42 Age [y:d:h:m:s]: 00:049:02:05:53
Block: 1414377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 35171 RingCT/type: yes/0
Extra: 0164f220eedba3791a38e7ad1eea8af48d656a0b609859c6a8473919a0db4fa0e0021100000003da554848000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ffc328ef0fe2e1b3c641e37463a8f0de6f7dfa158c7412f1f0c38ba1da9b9f9e 0.600000000000 1902866 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": 1414387, "vin": [ { "gen": { "height": 1414377 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ffc328ef0fe2e1b3c641e37463a8f0de6f7dfa158c7412f1f0c38ba1da9b9f9e" } } ], "extra": [ 1, 100, 242, 32, 238, 219, 163, 121, 26, 56, 231, 173, 30, 234, 138, 244, 141, 101, 106, 11, 96, 152, 89, 198, 168, 71, 57, 25, 160, 219, 79, 160, 224, 2, 17, 0, 0, 0, 3, 218, 85, 72, 72, 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