Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd9bd9c7872aeb18502c6188866c5434bf0e06f0453564849da4dcc8c84e6ef1

Tx prefix hash: e8d3481556af403c376c38a0cbcd9d4145fbeab17962e4a458e3b0e172f1aa2e
Tx public key: 0a942222f1e27194b6de9f418b8549bd1f5adc54999e2d4ba81b1b7c4c44d45c
Timestamp: 1721241901 Timestamp [UCT]: 2024-07-17 18:45:01 Age [y:d:h:m:s]: 01:114:08:24:16
Block: 1067864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 340220 RingCT/type: yes/0
Extra: 010a942222f1e27194b6de9f418b8549bd1f5adc54999e2d4ba81b1b7c4c44d45c02110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3942a5cbdeb69fd1a6d1803701c23f6ccb95f8f046f9e7f240176ad38670946f 0.600000000000 1538795 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": 1067874, "vin": [ { "gen": { "height": 1067864 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3942a5cbdeb69fd1a6d1803701c23f6ccb95f8f046f9e7f240176ad38670946f" } } ], "extra": [ 1, 10, 148, 34, 34, 241, 226, 113, 148, 182, 222, 159, 65, 139, 133, 73, 189, 31, 90, 220, 84, 153, 158, 45, 75, 168, 27, 27, 124, 76, 68, 212, 92, 2, 17, 0, 0, 0, 12, 145, 225, 60, 4, 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